Document Overview
| Document Category | Document Numbering Convention | Document Criteria | Where to Find | Document Managment | Maintained by |
|---|---|---|---|---|---|
|
DES Document Center Documents |
"CS or CSE" followed by a dash and a 3 or 4 digit number and an alpha code for document type. Example: CSE-1150A |
DES Document Center documents are managed by the DES Graphics Unit. These documents may exist in print, electronically or both. These documents are available to all DES staff and some are available to the public. |
1. DES Document Center on the internal and external DES website
|
Any DCSS employee may request creation, revision, or deletion of documents. Revision requests may be submitted on the Policy Revision Request Form. All document content must be reviewed and approved by Policy. Policy submits the request to DES Graphics and tracks the form request through completion. |
Documents in this category may be monitored for revisions by DCSS staff, Policy unit staff, Graphics unit staff. |
|
AZCARES Documents |
Cabinet name/number followed by document number followed by version number Example: FARI0001 F0026 002 |
Documents were created by the IM team and are generated manually by staff in the AZCARES Document generation screen (FCSE) or generated automatically in AZCARES by a specific action on a case (FARI). |
AZCARES |
Requests for revision to AZCARES documents may be submitted by DCSS staff by submitting a Policy Review Request Form. The document team are responsible for making all updates to the documents. All document content must be reviewed and approved by Policy. |
Documents in this category are maintained by the Eloquence team. |
|
Internal Documents |
No specified numbering convention |
This group of documents may includereferral forms, checklists, worksheets and internal forms. |
The PORT Document Matrix, Internal Forms and Checklists page, CSOA shared drives. |
Any DCSS employee may request creation, revision, or deletion of these documents. Revisions to this category of documents must be approved by the author of the document or a supervisor or manager within the primary user group |
Documents in this category are generally maintained in the region or unit which created them. |
| Vendor Documents | No specified numbering convention | Documents are specific to the DCSS. Documents are case and/or process specific. Documents are generated and maintained by a third-party vendor and distributed on behalf of the DCSS. | Vendor housed | Only staff associated with the specific functions addressed by these formrs are involved in the creation, revision or deletion of these documents. All document content must be reviewed and approved by Policy. |